Skip to content
This repository was archived by the owner on Jan 19, 2026. It is now read-only.

chore: internal docs for beta#187

Merged
alvarosabu merged 13 commits into
nextfrom
chore/internal-docs-for-beta
May 12, 2025
Merged

chore: internal docs for beta#187
alvarosabu merged 13 commits into
nextfrom
chore/internal-docs-for-beta

Conversation

@alvarosabu
Copy link
Copy Markdown
Contributor

This PR contains the temporary documentation for the Storyblok CLI v4 beta. Eventually, this will be moved to the official documentation

alvarosabu added 8 commits May 6, 2025 14:58
- Updated the main README to indicate that official documentation for package v4 is not yet available, directing users to the internal documentation for the v4 beta.
- Created a new README file in the src directory to provide detailed installation instructions and command references for the Storyblok CLI package.
- Added a comprehensive guide for the `login` command, including usage examples and options.
- Created a new README file for the `logout` command, detailing its usage, functionality, and examples.
- Included information on credential removal, session clearing, and warnings for already logged-out users.
- Aimed to enhance user understanding and provide clear instructions for the logout process.
- Created a new README file for the `languages` command, detailing its usage, options, and examples for pulling language configurations from a Storyblok space.
- Included information on file structure and notes for user requirements, enhancing clarity and usability for developers interacting with the command.
- Created a new README file for the `user` command, detailing its usage, functionality, and examples for viewing user information in Storyblok.
- Updated the main README to include a reference to the new `user` command, enhancing clarity and usability for developers interacting with the CLI.
- Aimed to provide comprehensive guidance for users to understand and utilize the command effectively.
- Updated the Command Reference section in the README to improve clarity and organization.
- Added a new Global Options section detailing options available for all commands, including descriptions and default values.
- Included a tip for users on providing verbose output when reporting bugs or support tickets to enhance troubleshooting.
- Removed unnecessary trailing whitespace from the README files for the `languages`, `login`, and `user` commands to improve formatting and maintain consistency across documentation.
- Ensured that all files end with a newline for better compatibility with various text editors.
… options

- Created detailed README files for the `components pull` and `components push` commands, outlining their usage, options, and examples for managing Storyblok components.
- Updated the main README to reference the new `components` module and its subcommands, enhancing clarity for developers.
- Adjusted option descriptions for consistency, including the removal of default values where applicable.
- Cleaned up the README files for the `components`, `components pull`, and `components push` commands by removing unnecessary trailing whitespace to improve formatting and maintain consistency across documentation.
- Ensured all files end with a newline for better compatibility with various text editors.
@alvarosabu alvarosabu added this to the v4-beta milestone May 6, 2025
@alvarosabu alvarosabu requested a review from edodusi May 6, 2025 15:08
@alvarosabu alvarosabu added the docs [Issue] Improvements or additions to documentation label May 6, 2025
- Created detailed README files for the `migrations`, `migrations generate`, and `migrations rollback` commands, outlining their usage, options, and examples for managing Storyblok component migrations.
- Updated the `migrations run` command documentation to include new options for publication modes and improved examples for clarity.
- Enhanced overall documentation structure to provide comprehensive guidance for developers interacting with the migrations functionality.
@pkg-pr-new
Copy link
Copy Markdown

pkg-pr-new Bot commented May 8, 2025

Open in StackBlitz

npm i https://pkg.pr.new/storyblok@187

commit: cafdb9d

Comment thread README.md Outdated
Comment thread README.md Outdated
> [!WARNING]
> Official documentation about this package v4 is not yet available. Please refer to the internal documentation for the [v4 beta](src/README.md).

~~For complete documentation, please visit [https://storyblok.com/docs](https://storyblok.com/docs/packages/my-joyful-package)~~
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would comment this out until we have the actual documentation link.

Comment thread src/README.md Outdated
Comment thread src/README.md
Comment on lines +7 to +17
For the latest beta version, install the package using the following command:

```bash
npm install storyblok@beta
```

Or for an specific beta version:

```bash
npm install storyblok@4.0.0-beta.<version>
```
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My suggestion is to keep the non-beta installation command in here. It makes sense for people to want the stable version for a new project.

Suggested change
For the latest beta version, install the package using the following command:
```bash
npm install storyblok@beta
```
Or for an specific beta version:
```bash
npm install storyblok@4.0.0-beta.<version>
```
Add the package to your project with the following command:
```bash
npm install storyblok@latest

You can also install the beta version, currently in development:

npm install storyblok@beta

It's also possible to target a specific beta version:

npm install storyblok@4.0.0-beta.<version>

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @alvarosabu, is this readme going to be in main, or in a beta branch? If it's supposed to be in main, I agree with @jeremenichelli.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, it's going to live on the next branch @manuelschroederdev @jeremenichelli these documentations are strictly for the beta since they will be replaced by official documentation later on

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's what I thought. 😄 Then feel free to disregard the suggestion from Jeremias here.

Comment thread src/README.md Outdated
Comment thread src/commands/languages/README.md Outdated
@@ -0,0 +1,100 @@
# Languages Command

The `languages` command allows you to manage languages in your Storyblok space. Currently, it supports pulling language configurations from your space.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The `languages` command allows you to manage languages in your Storyblok space. Currently, it supports pulling language configurations from your space.
The `languages` command allows you to handle internalization features within your Storyblok space. Currently, it supports pulling language configurations from your space.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @jeremenichelli @alvarosabu, I think both versions are a bit too bold. As it doesn't allow for managing anything at this point, we shouldn't raise any unrealistic expectations. If I'm not mistaken, this currently allows you to retrieve all configured languages as a JSON, similar to the spaces/me endpoint, correct?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Correct, it only allows pulling the languages available on the space @manuelschroederdev

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are there any plans to expand the functionality in the future?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@manuelschroederdev not in near future

Comment thread src/commands/migrations/run/README.md Outdated
Comment thread src/commands/migrations/run/README.md Outdated
Comment thread src/commands/types/generate/README.md Outdated
Comment thread src/commands/user/README.md Outdated
Comment thread src/commands/logout/README.md Outdated
Comment thread src/commands/migrations/generate/README.md Outdated
alvarosabu and others added 2 commits May 8, 2025 14:55
Co-authored-by: Jeremias Menichelli <jmenichelli@gmail.com>
- Removed outdated documentation reference from the main README.
- Renamed the "Command Reference" section to "API" in the src README for better alignment with content.
- Enhanced the API section by adding a status legend to clarify the readiness of commands.
- Updated the description of the `languages` command to specify its functionality more accurately.

These changes aim to improve the overall documentation quality and user experience for developers interacting with the Storyblok CLI.
alvarosabu added 2 commits May 8, 2025 15:24
- Eliminated an extra blank line in the main README to improve formatting and maintain consistency across documentation. This minor adjustment enhances readability for developers.
- Eliminated the note stating "You must be logged in to use this command" from the README files of various commands, including `pull`, `push`, `languages`, `migrations`, and `user`. This change aims to streamline the documentation and reduce redundancy, as the login requirement is already implied in the context of command usage.
Copy link
Copy Markdown
Contributor

@edodusi edodusi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@alvarosabu I don't have much to add here, to me the README are fine and I more or less have tested all the commands

@alvarosabu alvarosabu merged commit 55a2dd9 into next May 12, 2025
5 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

docs [Issue] Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants